Can we suppress the warning in code (as we did in 04cb1e3) and file a tracking issue to remove the suppression when we update to a 9.0 P7 SDK? Asking as P7 is still a month out.

The difference with 04cb1e3 is that we can't remove the suppression in code for that use case (since there's no replacement).

I assume you mainly don't want to carry a VMR patch for the next month?

The difference with 04cb1e3 is that we can't remove the suppression in code for that use case (since there's no replacement).

I'm interested in having a green stage 2 non-source-build. We don't have that in CI today but I do use the live produced from time to time to build the product just to see if there are any new breaking changes when updating to a newer SDK.

I assume you mainly don't want to carry a VMR patch for the next month?

Yes and no. I think it's fine to carry a patch for a month. But requiring a patch and not being able to apply the change directly in tree in the affected repo, sounds problematic.

Interesting. We added the new API and obsoleted the old API in the same preview release. That puts a lot pressure on our own product construction. cc @bartonjs @vcsjones

Filed #14936 to track removing the suppression, closing this for now.